Important notice about this release
===================================

We are very sorry to say that this release has an incorrect assembly version. 

This release should have been 2.0.12.91 and not 2.0.*13*.91

Next beta release will have the version value fixed.

What are the implications? 
==========================

The biggest problem is that this beta version will have a version number higher than the final 2.0.13 version. The final version will have an assembly version of 2.0.13.0 while this beta version has 2.0.13.91. As it is a beta and it is not supposed to be deployed in production systems, we think this won't give problems to our users.


How is Npgsql assembly versioned?
=================================

In the beginning, we used to use the same assembly version througout all the beta release cycle until the final release.
With this approach, Npgsql 2.0.10 beta1 would have the assembly version of 2.0.10.0 and beta2 would also have the assembly version of 2.0.10.0. This was creating confusion between users because they couldn't differentiate which version they were working with.

Starting with 2.0.11, we changed this in order to identify each version. We started to use the last two parts of the assembly version in order to identify beta releases. 
This way, a beta release was identified in the following form:
Npgsql 2.0.11 beta1 would be identified as: 2.0.10.91, beta2 would be identified as 2.0.10.92 and so on. With this schema, the beta versions will be incremented towards the final version 2.0.11.0.